KTOR-7825 Decrease Gradle memory consumption #4483
Open
+71
−15
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
osipxd
commented
Nov 15, 2024
osipxd
changed the title
osipxd
force-pushed
the
osipxd/decrease-memory-usage
branch
3 times, most recently
from
f633a1a
to
337ff73
Compare
osipxd
changed the title
osipxd
force-pushed
the
osipxd/decrease-memory-usage
branch
from
337ff73
to
c8e582d
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Subsystem
Build Infrastructure
Motivation
It is hard to build the project on machines with 16 GB RAM because of high memory consumption.
KTOR-7825 Reduce Gradle memory consumption
Solution
Xmxfor Kotlin Daemon (including the one used by Gradle to compile Kotlin DSL scripts)Xmxfor Gradle DaemonautoshutdownIdleSecondsfrom 2 hours to 30 minutes to mitigate buildSrc and buildSrc-like included builds spin up Kotlin daemon that for the most users used only once gradle/gradle#29331It would be great to specify
-XX:MaxMetaspaceSizeto prevent Gradle from being silently killed by OS due to unlimited metaspace consumption (see gradle/gradle#19750) and make memory consumption more predictable. Unfortunately, we can't do it now because of Kotlin/binary-compatibility-validator#282This is a WIP PR for those who are interested in trying the new daemon configurations.